You must have a separate CPGID.CP file for each AFP code page entry in the CPDEF.FNT file. Each code page map file contains the character identifiers (and associated EBCDIC hexadecimal code points) for an IBM code page and maps them to character identifiers (and associated ASCII code points) for a Windows ANSI or SYMBOL character set. Code page map files are necessary for basic multiple code page support.
The actual file name is not CPGID.CP, but rather the CPGID value from the CPDEF.FNT file with an extension of CP. For instance, in the CPDEF.FNT example, the first two lines are:
T100ASC4=361,ANSI
T1DOC037=37,ANSI
So, since those two entries are in the CPDEF.FNT file, that means that there must be code page map files with named 361.CP and 37.CP.
Also, if these two entries are in the CPDEF.FNT file, but the corresponding 361.CP and 37.CP code page map files are not in DEFLIB, the translations for those fonts will not be correct.
When creating this file, keep these rules in mind:
Here is an example of this file: (395.cp for the T1000395 code page mapped to the Windows ANSI character set):
;T1000395 to ANSI
SP010000 40 SP010000 20
LA150000 42 LA150000 E2
LA170000 43 La170000 E4
LA130000 44 LA130000 E0
SP180000 8B SP180000 BB
SM560000 8C SM560000 89
SA000000 8D SP100000 2D
LI510000 8E NOMATCH 00
LI570000 8F NOMATCH 00
SM190000 90 SM190000 B0
LJ010000 91 LJ010000 6A
LF510000 A0 NOMATCH 00
;;;;;;;; ; SD150000 5E
;;;;;;;; ; SD130000 60
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.